Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jan30: Part One #649

Merged
merged 18 commits into from
Feb 3, 2024
Merged

Jan30: Part One #649

merged 18 commits into from
Feb 3, 2024

Conversation

hobinjk
Copy link
Collaborator

@hobinjk hobinjk commented Jan 30, 2024

https://en-forum.guildwars2.com/topic/142673-game-update-notes-january-30-2024/

Elementalist

  • Hammer outdated

Engineer

  • Pistol outdated? "Blowtorch: Fixed an issue that caused this skill to inflict more burning than intended."
  • Applied Force: Reduced the bonus power per might stack from 35 to 30 in PvE only.

Guardian

  • Torch outdated

Mesmer

  • Axe outdated
  • Illusionary Membrane: Reduced the condition damage bonus from 10% to 7% in PvE only.
  • Chaotic Persistence: unchanged (new from preview)

Ranger

  • Untamed Axe outdated
  • Greatsword outdated
  • Devourer outdated

Revenant

  • Leviathan Strength: Reduced the damage bonus from 15% to 10% in PvE only.

Warrior

  • Blood Reaction: Increased the precision to ferocity conversion from 10% to 12% in PvE only.
  • Bloody Roar: Reduced the damage bonus from 20% to 15% in PvE only.

Miscellaneous

  • Update disclaimer

The distribution between quick/alac is identical so this condenses the
Quick and Alac Power Chrono templates into Boon Power Chrono
Staxe is now very strong but only for pure condi damage
It didn't change much at all
RIP the one ele hammer build I managed to update
> Blowtorch: Fixed an issue that caused this skill to inflict more burning than intended.

Condi Holo moving from where it is to somewhere else
In theory a positive QoL change!
> Illusionary Membrane: Reduced the condition damage bonus from 10% to 7% in PvE only.
Unsplit!

> Leviathan Strength: Reduced the damage bonus from 15% to 10% in PvE only.
https://wiki.guildwars2.com/wiki/Blood_Reaction

Conversion buffed in PvE. Conversion was wrong in WvW

Bloody roar nerfed in PvE.
@marcustyphoon
Copy link
Collaborator

Does this invalidate the power berserker template? (Not sure if it was already kind of out of date, but.)

@hobinjk
Copy link
Collaborator Author

hobinjk commented Feb 3, 2024

I marked it as outdated (#650?). It's a bit overly long text-wise to have both Approx and Outdated but I plan to bring it back to just Approx soon-ish

@marcustyphoon
Copy link
Collaborator

Yeah—do these changes make it any more out of date, though?

@marcustyphoon
Copy link
Collaborator

(Well —I suppose its coefficients being theoretically unchanged would only be correct if we have a perfect figure for what percentage of your damage is affected by berserk, which we probably don't. And in any case if it's to be updated soon it may as well be marked outdated :D)

Copy link
Contributor

github-actions bot commented Feb 3, 2024

Deployed preview build to Cloudflare!

Last commit: b7f85d0
Preview URL: https://7f76ba9c.discretize-optimizer.pages.dev
Branch Preview URL: https://jan30-part-one.discretize-optimizer.pages.dev

@hobinjk
Copy link
Collaborator Author

hobinjk commented Feb 3, 2024

Oh, in this PR it's "Power Berserker (Approx.) (Outdated)." A bit long (and a bit parenthetical). The template was up-to-date before the trait changes

I have a script for accurate damage per weapon but not for damage in berserk, could add that for the sake of science (I really should integrate all of these random scripts I'm writing into the developer section where they belong)

@marcustyphoon
Copy link
Collaborator

Oh, looks like it is, yeah. And not updated since the infinite berserk change, it seems, which gave it another signet.

@marcustyphoon marcustyphoon merged commit d34ecc9 into main Feb 3, 2024
3 checks passed
@marcustyphoon marcustyphoon deleted the jan30-part-one branch February 3, 2024 05:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants